• Helper/AdyenOrderPayment.php
  • Modified createAdyenOrderPayment method signature to accept explicit payment details (PSP reference, payment method, amount value, amount currency) instead of a Notification object.
  • Updated the merchantReference to use order->getIncrementId() directly.
  • Changed captureStatus constant reference from Payment to OrderPaymentInterface.
  • Adjusted error logging to use order->getIncrementId() for merchant reference.
• Helper/Invoice.php
  • Modified createInvoice method signature to accept explicit payment details (PSP reference, amount value) instead of a Notification object.
  • Updated logging contexts to use pspReference and order->getIncrementId() directly.
  • Changed invoice->setTransactionId to use the passed pspReference.
  • Updated value for offline invoice creation to use the passed amountValue.
  • Simplified error and warning messages.
• Helper/Order.php
  • Modified updatePaymentDetails method signature to accept pspReference directly instead of a Notification object.
  • Updated setCcTransId, setLastTransId, and setTransactionId to use the passed pspReference.
  • Modified finalizeOrder method signature to accept pspReference and amount directly instead of a Notification object.
  • Removed Boleto-specific status handling logic (getBoletoStatus) and the addProcessedStatusHistoryComment call.
  • Updated logging contexts to use pspReference and order->getIncrementId().
• Helper/PaymentMethods.php
  • Removed the getBoletoStatus method, which handled Boleto-specific overpaid/underpaid status logic.
• Helper/PaymentResponseHandler.php
  • Added AuthorizationHandler as a dependency.
  • Integrated AuthorizationHandler::execute to authorize payments when resultCode is AUTHORISED in handlePaymentsDetailsResponse.
• Helper/Webhook/AuthorisationWebhookHandler.php
  • Refactored constructor dependencies, removing AdyenOrderPayment, CaseManagement, Invoice, PaymentMethods helpers and adding AuthorizationHandler and AdyenOrderPayment resource model.
  • Converted class to readonly.
  • Significantly refactored handleSuccessfulAuthorisation to delegate all core authorization logic to the new AuthorizationHandler.
  • Removed markPaymentCapturedIfNeeded, sendOrderMailIfNeeded, createCashShipmentIfNeeded, handleAutoCapture, and handleManualCapture methods, as their logic is now centralized in AuthorizationHandler.
  • Added a fallback mechanism to ensure order payment is created during webhook handling if not already present.
• Helper/Webhook/CaptureWebhookHandler.php
  • Modified finalizeOrder call to pass pspReference and amountValue explicitly instead of the Notification object.
• Helper/Webhook/ManualReviewAcceptWebhookHandler.php
  • Modified finalizeOrder call to pass pspReference and amountValue explicitly instead of the Notification object.
• Model/AuthorizationHandler.php
  • Added a new class AuthorizationHandler to centralize payment authorization logic.
  • Contains execute method that orchestrates the creation of adyen_order_payment entries, updates payment details, handles auto-capture (creating invoices, finalizing orders), and manual capture (marking for review or adding comments).
  • Includes private helper methods handleAutoCapture, handleManualCapture, and sendOrderMailIfNeeded.
• Observer/AuthorizeAfterOrderPlacement.php
  • Added a new observer AuthorizeAfterOrderPlacement that listens to the checkout_submit_all_after event.
  • Retrieves stored payment responses for the order.
  • If an AUTHORISED payment response is found, it uses the AuthorizationHandler to process the authorization, ensuring the order state is correctly updated.
• Test/Unit/Helper/PaymentMethodsTest.php
  • Removed unit tests for the getBoletoStatus method, as the method itself was removed.
• etc/events.xml
  • Added a new observer adyen_authorize_payment_after_order_placement for the checkout_submit_all_after event.

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.